📨Active AMQ

Task Manager & Message Queue Operations

Operation Title: Active AMQ

Over view: Monitor and Manage Messaging Queues in Real Time.

Key Features:

  • o Functionality and Refresh
  • Select the Services (UAT/PROD)
  • Region Selection (Precondition)
  • Access AMQ update Form
  • Active AMQ Records Table
  • Consumers Explanation
  • AMQ Operations Panel
  • AMQ Status Display
  • Send To – API Request Setup
  • Final Output – AMQ summury

List of Figures:

  • Figure 11.1 – Refresh Button and Service Selection
  • Figure 11.2 – Region Selection Before Opening Task Manager
  • Figure 11.3 – Active AMQ Records Table and Consumers View
  • Figure 11.4 – AMQ Operations Panel with Column Display
  • Figure 11.5 – AMQ Status Panel (Consumer & Message Count)
  • Figure 11.6 – API Header, Value and Body Setup (Send To)
  • Figure 11.7 – Purge Queue Action with Warning
⚡Overview

From the Task Manager, users can assign tasks to team members and define task details such as descriptions, deadlines, and priorities. This centralized interface helps streamline task delegation and ensures accountability by tracking assigned responsibilities in one place.

⚡Introduction

The Task Manager is a built-in feature of the application designed to help users efficiently assign, manage, and track tasks within a collaborative workspace. It simplifies team coordination by allowing users to define task details, monitor progress, and ensure timely completion of responsibilities all from a centralized, user-friendly interface.

⚙️Functionality

Figure: 11.1
1. Select the Services:

Choose the target server (UAT or Production) to apply actions in the correct environment.

2. Refresh Button:
Red Circular Arrows:

Refreshes the table to display the latest updated data.

How to use the AMQ Update form?
NOTE:

Before open the Task manager form, users must select the region from navbar

Figure: 11.2

📊Active AMQ Records Table

3. Active AMQ Records table:
Record Information
Name:
Displays the name of the user for easy identification within the system.
Pending:
Pending refers to the number of messages that are currently in the queue but have not yet been consumed or processed by any consumer. It indicates the backlog or workload waiting to be handled in the messaging system.
Figure: 11.3
Consumers:

Consumers are applications or services that receive and process messages from a message queue. In a messaging system like ActiveMQ, consumers listen to specific queues or topics, retrieve incoming messages, and take appropriate actions based on the message content. They play a crucial role in asynchronous communication, workload distribution, and system integration.

Figure: 11.4

🔧AMQ Operations

AMQ Operations:
AMQ Status:

This section displays the status of the io.az.jms.voyager-remittance-notif-QUEUE, including key metrics such as consumer count and message count. It helps monitor message flow and queue health for effective system performance tracking.

Figure: 11.5
Send It:

Here, users can define the request's header key and value, and specify the body type to ensure the API call is properly formatted for accurate and secure communication.

Figure: 11.6

🗑️Purge Operations

Purge:

Upon triggering the Purge button (as illustrated in the image below), all messages contained within the selected queue are permanently removed. This function is typically used to eliminate obsolete, failed, or excess messages, ensuring the queue remains optimized for active processing. It is important to note that purging is irreversible and should be executed with caution.

⚠️ CAUTION: Purge Operation
• All messages in the selected queue will be permanently deleted
• This operation is irreversible
• Ensure queue backup if needed before executing
• Used for removing obsolete, failed, or excess messages
• Optimizes queue performance for active processing
Execute with proper authorization and verification
Figure: 11.7

🎯Final Output & Results

Final Output:

After performing actions in the Active AMQ interface such as sending messages, purging queues, or monitoring consumer activity the updated status and message data are reflected in the records table. Users can verify successful operations, track queue performance, and confirm that outdated or processed messages have been handled. This final output ensures transparency, helps maintain system health, and supports real-time queue management.

Key Benefits of AMQ Operations:
  • Real-time Status Updates: Immediate reflection of changes in the records table
  • Operation Verification: Confirm successful completion of AMQ operations
  • Queue Performance Tracking: Monitor message flow and consumer activity
  • Message Management: Handle outdated or processed messages efficiently
  • System Transparency: Clear visibility into queue operations and status
  • Health Monitoring: Maintain optimal system performance
  • Real-time Management: Support for live queue management operations
  • Error Detection: Quick identification of issues and anomalies
Sample AMQ Status Output:
Queue: io.az.jms.voyager-remittance-notif-QUEUE
Status: Active
Consumer Count: 3
Pending Messages: 127
Processed Messages: 1,890
System Health: Optimal